GML feature collections (A set of XML documents. Each document contains a GML feature collection.)
Feature statistics
Type
Total Count
all
5
ManagementRestrictionOrRegulationZone
5
Log path: Conformance class: INSPIRE GML encoding
Testing 5 features
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data-encoding/inspire-gml/ets-inspire-gml-bsxets.xml
Statistics table: 11 ms
Test Suite 'Conformance class: INSPIRE GML encoding' started
Test Case 'Basic tests' started
Test Assertion 'gml.a.1: Errors loading the XML documents': PASSED - 0 ms
Test Assertion 'gml.a.2: Document root element': PASSED - 0 ms
Test Assertion 'gml.a.3: Character encoding': NOT_APPLICABLE
Test Case 'Basic tests' finished: PASSED
Test Suite 'Conformance class: INSPIRE GML encoding' finished: PASSED
Log path: Conformance class: Reference systems, General requirements
Testing 5 features
Indexing features (parsing errors: 0): 223 ms
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data/reference-systems/ets-reference-systems-bsxets.xml
Statistics table: 11 ms
Test Suite 'Conformance class: Reference systems, General requirements' started
Test Case 'Spatial reference systems' started
Test Assertion 'rs.a.1: Spatial reference systems in feature geometries': PASSED - 0 ms
Test Assertion 'rs.a.2: Default spatial reference systems in feature collections': PASSED - 0 ms
Test Case 'Spatial reference systems' finished: PASSED
Test Case 'Temporal reference systems' started
Test Assertion 'rs.a.3: Temporal reference systems in features': PASSED - 2 ms
Test Case 'Temporal reference systems' finished: PASSED
Test Suite 'Conformance class: Reference systems, General requirements' finished: PASSED
Log path: Conformance class: Reference systems, Area Management, Restriction/Regulation Zones
and Reporting Units
Testing 5 features
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data-am/am-rs/ets-am-rs-bsxets.xml
Statistics table: 24 ms
Test Suite 'Conformance class: Reference systems, Area Management, Restriction/Regulation Zones and Reporting Units' started
Test Case 'Additional theme-specific rules for reference systems' started
Test Assertion 'am-rs.a.1: Test always passes': PASSED - 0 ms
Test Case 'Additional theme-specific rules for reference systems' finished: PASSED
Test Suite 'Conformance class: Reference systems, Area Management, Restriction/Regulation Zones and Reporting Units' finished: PASSED
Log path: Conformance class: Information accessibility, General requirements
Testing 5 features
Indexing features (parsing errors: 0): 158 ms
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data/information-accessibility/ets-information-accessibility-bsxets.xml
Statistics table: 10 ms
Test Suite 'Conformance class: Information accessibility, General requirements' started
Test Case 'Coordinate reference systems (CRS)' started
Checking URL: 'http://www.opengis.net/def/crs/EPSG/0/4258'
Test Assertion 'ia.a.1: CRS publicly accessible via HTTP': PASSED - 9 ms
Test Case 'Coordinate reference systems (CRS)' finished: PASSED
Test Suite 'Conformance class: Information accessibility, General requirements' finished: PASSED
Log path: Conformance class: Information accessibility, Area Management, Restriction/Regulation
Zones and Reporting Units
Testing 5 features
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data-am/am-ia/ets-am-ia-bsxets.xml
Statistics table: 12 ms
Test Suite 'Conformance class: Information accessibility, Area Management, Restriction/Regulation Zones and Reporting Units' started
Test Case 'Code list' started
Test Assertion 'am-ia.a.1: zoneType': PASSED - 1 ms
Checking URL: 'http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/ENDAgglomeration'
Checking URL: 'http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/ENDAgglomeration'
Checking URL: 'http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/ENDAgglomeration'
Checking URL: 'http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/ENDAgglomeration'
Checking URL: 'http://dd.eionet.europa.eu/vocabulary/inspire/SpecialisedZoneTypeCode/ENDAgglomeration'
Test Assertion 'am-ia.a.2: specialisedZoneType': PASSED - 490 ms
Test Case 'Code list' finished: PASSED
Test Case 'Feature references' started
Test Assertion 'am-ia.b.1: relatedZone': PASSED - 0 ms
Test Assertion 'am-ia.b.2: plan': PASSED - 0 ms
Checking URL: 'http://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'https://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'http://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'https://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'http://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'https://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'http://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'https://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'http://data.europa.eu/eli/dir/2002/49/oj'
Checking URL: 'https://data.europa.eu/eli/dir/2002/49/oj'
Test Assertion 'am-ia.b.3: legalBasis': PASSED - 23169 ms
Test Case 'Feature references' finished: PASSED
Test Suite 'Conformance class: Information accessibility, Area Management, Restriction/Regulation Zones and Reporting Units' finished: PASSED
Log path: Conformance class: Data consistency, General requirements
Testing 5 features
Indexing features (parsing errors: 0): 135 ms
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data/data-consistency/ets-data-consistency-bsxets.xml
Statistics table: 9 ms
Test Suite 'Conformance class: Data consistency, General requirements' started
Test Case 'Version consistency' started
Test Assertion 'dc.a.1: Version lifespan plausible': PASSED - 1 ms
Test Assertion 'dc.a.2: Unique identifier persistency': PASSED_MANUAL
Test Assertion 'dc.a.3: Spatial object type stable': PASSED_MANUAL
Test Case 'Version consistency' finished: PASSED_MANUAL
Test Case 'Temporal consistency' started
Test Assertion 'dc.b.1: Valid time plausible': PASSED - 0 ms
Test Case 'Temporal consistency' finished: PASSED
Test Suite 'Conformance class: Data consistency, General requirements' finished: PASSED_MANUAL
Log path: Conformance class: Data consistency, Area Management, Restriction/Regulation Zones
and Reporting Units
Testing 5 features
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data-am/am-dc/ets-am-dc-bsxets.xml
Statistics table: 31 ms
Test Suite 'Conformance class: Data consistency, Area Management, Restriction/Regulation Zones and Reporting Units' started
Test Case 'Geometry consistency' started
Test Assertion 'am-dc.a.1: Geometry consistency': PASSED_MANUAL
Test Case 'Geometry consistency' finished: PASSED_MANUAL
Test Suite 'Conformance class: Data consistency, Area Management, Restriction/Regulation Zones and Reporting Units' finished: PASSED_MANUAL
Log path: Conformance class: INSPIRE GML application schemas, General requirements
Testing 5 features
Indexing features (parsing errors: 0): 202 ms
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data/schemas/ets-schemas-bsxets.xml
Statistics table: 20 ms
Test Suite 'Conformance class: INSPIRE GML application schemas, General requirements' started
Test Case 'Schema' started
Test Assertion 'gmlas.a.1: Mapping of source data to INSPIRE': PASSED_MANUAL
Test Assertion 'gmlas.a.2: Modelling of additional spatial object types': PASSED_MANUAL
Test Case 'Schema' finished: PASSED_MANUAL
Test Case 'Validation against declared schema' started
Test Assertion 'gmlas.b.1: xsi:schemaLocation attribute': PASSED - 0 ms
Validating DF1_5_Aggl_AT.03.07.23.gml
Duration: 500 ms. Errors: 0.
Test Assertion 'gmlas.b.2: validate XML documents against declared schema': PASSED - 818 ms
Test Case 'Validation against declared schema' finished: PASSED
Test Case 'GML model' started
Test Assertion 'gmlas.c.1: Consistency with the GML model': PASSED - 5 ms
Test Assertion 'gmlas.c.2: nilReason attributes require xsi:nil=true': PASSED - 0 ms
Test Assertion 'gmlas.c.3: nilReason values': PASSED - 0 ms
Test Case 'GML model' finished: PASSED
Test Case 'Simple features' started
Test Assertion 'gmlas.d.1: No spatial topology objects': PASSED - 3 ms
Test Assertion 'gmlas.d.2: No non-linear interpolation': PASSED - 0 ms
Test Assertion 'gmlas.d.3: Surface geometry elements': PASSED - 2 ms
Test Assertion 'gmlas.d.4: No non-planar interpolation': PASSED - 0 ms
Test Assertion 'gmlas.d.5: Geometry elements': PASSED - 1 ms
Test Assertion 'gmlas.d.6: Point coordinates in gml:pos': PASSED - 1 ms
Test Assertion 'gmlas.d.7: Curve/Surface coordinates in gml:posList': PASSED - 1 ms
Test Assertion 'gmlas.d.8: No array property elements': PASSED - 1 ms
Test Assertion 'gmlas.d.9: 1, 2 or 3 coordinate dimensions': PASSED - 0 ms
Test Assertion 'gmlas.d.10: Validate geometries (1)': PASSED - 533 ms
Test Assertion 'gmlas.d.11: Validate geometries (2)': PASSED - 0 ms
Test Case 'Simple features' finished: PASSED
Test Case 'Code list values in basic data types' started
Test Assertion 'gmlas.e.1: GrammaticalNumber attributes': PASSED - 15 ms
Test Assertion 'gmlas.e.2: GrammaticalGender attributes': PASSED - 27 ms
Test Assertion 'gmlas.e.3: NameStatus attributes': PASSED - 14 ms
Test Assertion 'gmlas.e.4: Nativeness attributes': PASSED - 8 ms
Test Case 'Code list values in basic data types' finished: PASSED
Test Case 'Constraints' started
Test Assertion 'gmlas.f.1: At least one of the two attributes pronunciationSoundLink and pronunciationIPA shall not be void': PASSED - 0 ms
Test Case 'Constraints' finished: PASSED
Test Suite 'Conformance class: INSPIRE GML application schemas, General requirements' finished: PASSED_MANUAL
Log path: Conformance class: GML application schemas, Area Management, Restriction/Regulation
Zones and Reporting Units
Testing 5 features
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data-am/am-gml/ets-am-gml-bsxets.xml
Statistics table: 9 ms
Test Suite 'Conformance class: GML application schemas, Area Management, Restriction/Regulation Zones and Reporting Units' started
Test Case 'Basic test' started
Test Assertion 'am-gml.a.1: ManagementRestrictionOrRegulationZone feature in dataset': PASSED - 0 ms
Test Case 'Basic test' finished: PASSED
Test Case 'Validation against INSPIRE official schema' started
Validating DF1_5_Aggl_AT.03.07.23.gml
Duration: 279 ms. Errors: 0.
Test Assertion 'am-gml.b.1: validate XML documents against official schema': PASSED - 301 ms
Test Case 'Validation against INSPIRE official schema' finished: PASSED
Test Suite 'Conformance class: GML application schemas, Area Management, Restriction/Regulation Zones and Reporting Units' finished: PASSED
Log path: Conformance class: Application Schema, Area Management, Restriction/Regulation Zones
and Reporting Units
Testing 5 features
Executing Test Suite: /etf/projects/inspire-ets-repository/ets-repository-2023.2/data-am/am-as/ets-am-as-bsxets.xml
Statistics table: 9 ms
Test Suite 'Conformance class: Application Schema, Area Management, Restriction/Regulation Zones and Reporting Units' started
Test Case 'Code list values' started
Test Assertion 'am-as.a.1: EnvironmentalDomain code list value': PASSED - 246 ms
Test Assertion 'am-as.a.2: zoneType code list value': PASSED - 193 ms
Test Case 'Code list values' finished: PASSED
Test Case 'Constraints' started
Test Assertion 'am-as.b.1: Constraint for legalBasis': PASSED_MANUAL - 0 ms
Test Assertion 'am-as.b.2: Constraint for competentAuthority': PASSED - 0 ms
Test Case 'Constraints' finished: PASSED_MANUAL
Test Suite 'Conformance class: Application Schema, Area Management, Restriction/Regulation Zones and Reporting Units' finished: PASSED_MANUAL
Conformance class: INSPIRE GML encoding
1
This test suite examines GML documents against basic requirements for the GML encoding for spatial data sets in INSPIRE. This only covers application-schema-independent, generic requirements. Requirements related to specific application schemas are part of conformance classes with a dependency on this conformance class.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion.
Report errors that occurred during loading the documents in the test object. A typical example is an XML document that is not well-formed and therefore cannot be processed.
Check for each XML document that the root element is a GML feature or a GML feature collection.
For feature collections the following root elements are recognised:
wfs:FeatureCollection (WFS 2.0),
gml:FeatureCollection (GML 3.2),
base:SpatialDataSet (INSPIRE Base 3.2 or 3.3).
This test is a pre-condition to identify the INSPIRE features in the test object.
Relevant requirements and recommendations:
Recommendation 11 - For the exchange of spatial objects in GML, an XML document with a FeatureCollection root element from ISO 19142:2010 (WFS 2.0) should be used.
Known limitations:
Currently only feature collections are recognized as the test engine BaseX is not schema-aware. A new extension function would be required to identify all feature elements.
This test ensures that all linguistic texts can be encoded consistently and in any language – which in turn simplifies the processing of data. The use of UTF-8 also aligns with common practice and is the default character encoding for XML documents.
Inspect each XML document. If an XML declaration exists, verify that the encoding attribute has the value "UTF-8" or that the attribute is missing.
Relevant requirements:
Requirement 12 - XML documents shall be required to be encoded using UTF-8 as character encoding.
Known limitations:
Currently the test is disabled as the test needs an BaseX extension - the XML declaration is NOT part of the node set in XML databases.
Conformance class: Reference systems, General requirements
2
This test suite examines a data set against the basic requirements related to reference systems (spatial and temporal, units of measurement). This test suite only examines requirements that are not specific to a data theme. Additional test cases will be defined per data theme, where needed.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
Verify that all references to coordinate reference systems in the features (srsName) use one of the approved CRS URIs listed in TG requirement 2.
Relevant requirements:
IR Requirement Annex II Section 1.2: Datum for three-dimensional and two-dimensional coordinate reference systems. For the three-dimensional and two-dimensional coordinate reference systems and the horizontal component of compound coordinate reference systems used for making spatial data sets available, the datum shall be the datum of the European Terrestrial Reference System 1989 (ETRS89) in areas within its geographical scope, or the datum of the International Terrestrial Reference System (ITRS) or other geodetic coordinate reference systems compliant with ITRS in areas that are outside the geographical scope of ETRS89. Compliant with the ITRS means that the system definition is based on the definition of the ITRS and there is a well documented relationship between both systems, according to EN ISO 19111.
IR Requirement Annex II Section 1.3: Datum for three-dimensional and two-dimensional coordinate reference systems. Spatial data sets shall be made available using at least one of the coordinate reference systems:
Two-dimensional geodetic coordinates (latitude and longitude) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.
Plane coordinates using the ETRS89 Lambert Azimuthal Equal Area coordinate reference system.
Plane coordinates using the ETRS89 Lambert Conformal Conic coordinate reference system.
Plane coordinates using the ETRS89 Transverse Mercator coordinate reference system.
Compound coordinate reference system using one of the systems above plus, for the vertical component, one of the following coordinate reference systems shall be used:
For the vertical component on land, the European Vertical Reference System (EVRS) shall be used to express gravity-related heights within its geographical scope. Other vertical reference systems related to the Earth gravity field shall be used to express gravity-related heights in areas that are outside the geographical scope of EVRS.
For the vertical component in the free atmosphere, barometric pressure, converted to height using ISO 2533:1975 International Standard Atmosphere, or other linear or parametric reference systems shall be used. Where other parametric reference systems are used, these shall be described in an accessible reference using EN ISO 19111-2:2012.
For the vertical component in marine areas where there is an appreciable tidal range (tidal waters), the Lowest Astronomical Tide (LAT) shall be used as the reference surface.
For the vertical component in marine areas without an appreciable tidal range, in open oceans and effectively in waters that are deeper than 200 meters, the Mean Sea Level (MSL) or a well- defined reference level close to the MSL shall be used as the reference surface.
Three-dimensional Cartesian coordinates based on a datum specified in 1.2 and using the parameters of the Geodetic Reference System 1980 (GRS80) ellipsoid.
Three-dimensional geodetic coordinates (latitude, longitude and ellipsoidal height) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.
For regions outside of continental Europe, Member States may define suitable coordinate reference systems. The geodetic codes and parameters needed to describe these coordinate reference systems and to allow conversion and transformation operations shall be documented and an identifier shall be created, according to EN ISO 19111 and ISO 19127.
IR Requirement Annex II Section 1.5 (1): Coordinate Reference System Identifiers. Coordinate reference system parameters and identifiers shall be managed in one or several common registers for coordinate reference systems.
IR Requirement Annex II Section 1.5 (2): Coordinate Reference System Identifiers. Only identifiers contained in a common register shall be used for referring to the coordinate reference systems listed in this Section.
Verify that all references to coordinate reference systems in the bounding box of the feature collection (srsName) use one of the CRS URIs listed in TG requirement 2.
Relevant requirements:
IR Requirement Annex II Section 1.2: Datum for three-dimensional and two-dimensional coordinate reference systems. For the three-dimensional and two-dimensional coordinate reference systems and the horizontal component of compound coordinate reference systems used for making spatial data sets available, the datum shall be the datum of the European Terrestrial Reference System 1989 (ETRS89) in areas within its geographical scope, or the datum of the International Terrestrial Reference System (ITRS) or other geodetic coordinate reference systems compliant with ITRS in areas that are outside the geographical scope of ETRS89. Compliant with the ITRS means that the system definition is based on the definition of the ITRS and there is a well documented relationship between both systems, according to EN ISO 19111.
IR Requirement Annex II Section 1.3: Datum for three-dimensional and two-dimensional coordinate reference systems. Spatial data sets shall be made available using at least one of the coordinate reference systems:
Two-dimensional geodetic coordinates (latitude and longitude) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.
Plane coordinates using the ETRS89 Lambert Azimuthal Equal Area coordinate reference system.
Plane coordinates using the ETRS89 Lambert Conformal Conic coordinate reference system.
Plane coordinates using the ETRS89 Transverse Mercator coordinate reference system.
Compound coordinate reference system using one of the systems above plus, for the vertical component, one of the following coordinate reference systems shall be used:
For the vertical component on land, the European Vertical Reference System (EVRS) shall be used to express gravity-related heights within its geographical scope. Other vertical reference systems related to the Earth gravity field shall be used to express gravity-related heights in areas that are outside the geographical scope of EVRS.
For the vertical component in the free atmosphere, barometric pressure, converted to height using ISO 2533:1975 International Standard Atmosphere, or other linear or parametric reference systems shall be used. Where other parametric reference systems are used, these shall be described in an accessible reference using EN ISO 19111-2:2012.
For the vertical component in marine areas where there is an appreciable tidal range (tidal waters), the Lowest Astronomical Tide (LAT) shall be used as the reference surface.
For the vertical component in marine areas without an appreciable tidal range, in open oceans and effectively in waters that are deeper than 200 meters, the Mean Sea Level (MSL) or a well- defined reference level close to the MSL shall be used as the reference surface.
Three-dimensional Cartesian coordinates based on a datum specified in 1.2 and using the parameters of the Geodetic Reference System 1980 (GRS80) ellipsoid.
Three-dimensional geodetic coordinates (latitude, longitude and ellipsoidal height) based on a datum specified in 1.2 and using the parameters of the GRS80 ellipsoid.
For regions outside of continental Europe, Member States may define suitable coordinate reference systems. The geodetic codes and parameters needed to describe these coordinate reference systems and to allow conversion and transformation operations shall be documented and an identifier shall be created, according to EN ISO 19111 and ISO 19127.
IR Requirement Annex II Section 1.5 (1): Coordinate Reference System Identifiers. Coordinate reference system parameters and identifiers shall be managed in one or several common registers for coordinate reference systems.
IR Requirement Annex II Section 1.5 (2): Coordinate Reference System Identifiers. Only identifiers contained in a common register shall be used for referring to the coordinate reference systems listed in this Section.
Verify that all references to coordinate reference systems in the features use one of the approved http URIs, i.e. check that all references to coordinate reference systems in the frame XML attributes in the features use the URI 'http://www.opengis.net/def/trs/ISO-8601/'.
Note that all values in the XML Schema date/time types is automatically in the required reference system.
Relevant requirements:
IR Requirement Article 11 (1): Temporal Reference Systems. The default temporal reference system referred to in point 5 of part B of the Annex to Commission Regulation (EC) No 1205/2008 (14) shall be used, unless other temporal reference systems are specified for a specific spatial data theme in Annex II.
Conformance class: Reference systems, Area Management, Restriction/Regulation Zones
and Reporting Units
1
This test suite examines a data set against the theme-specific requirements related to reference systems (spatial and temporal, units of measurement).
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
This conformance class includes no assertions beyond the ones referenced by dependencies, i.e. those that apply across the data themes. This assertion will always pass and is included for technical reasons.
Conformance class: Information accessibility, General requirements
1
This test suite examines a data set against the basic requirements related to the accessibility of resources referenced by the data. This test suite only examines requirements that are not specific to a data theme. Additional test cases will be defined per data theme, where needed.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
Verify that any coordinate reference system is publicly accessible via HTTP, i.e. inspect links to coordinate reference systems. Verify that a HTTP GET request to the URI of each unique link (srsName, frame) retrieves a document.
Relevant requirements:
IR Requirement Article 10 (3): Life-cycle of Spatial Objects. Where the attributes beginLifespanVersion and endLifespanVersion are used, the value of endLifespanVersion shall not be before the value of beginLifespanVersion.
Conformance class: Information accessibility, Area Management, Restriction/Regulation
Zones and Reporting Units
2
This test suite examines a data set against the themespecific requirements related to the accessibility of resources referenced by the data.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
Verify that any zoneType code list is publicly accessible via HTTP. If a reference (@xlink:href) has a value that does not start with http://inspire.ec.europa.eu/codelist/, verify that a HTTP GET request to the URI retrieves a document.
Verify that any specialisedZoneType code list is publicly accessible via HTTP. If a reference (@xlink:href) has a value that does not start with http://inspire.ec.europa.eu/codelist/, verify that a HTTP GET request to the URI retrieves a document.
Verify that any relatedZone reference is publicly accessible via HTTP. If a reference (@xlink:href) has a value that starts with "#", verify that an element with a 'gml:id' attribute with the referenced identifier exists in the same document. If the reference starts with "http", verify that a HTTP GET request to the URI retrieves a document.
Verify that any plan reference is publicly accessible via HTTP. If a reference (@xlink:href) has a value that starts with "#", verify that an element with a 'gml:id' attribute with the referenced identifier exists in the same document. If the reference starts with "http", verify that a HTTP GET request to the URI retrieves a document.
Verify that any legalBasis reference is publicly accessible via HTTP. If a reference (@xlink:href) has a value that starts with "#", verify that an element with a 'gml:id' attribute with the referenced identifier exists in the same document. If the reference starts with "http", verify that a HTTP GET request to the URI retrieves an XML document.
Conformance class: Data consistency, General requirements
2
This test suite examines a data set against the basic requirements related to the consistency of the data. This test suite only examines requirements that are not specific to a data theme. Additional test cases will be defined per data theme, where needed.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
Verify that all endLifespanVersion values are from the allowed range. For all features verify that either
beginLifespanVersion or endLifespanVersion are missing or nil or
endLifespanVersion is not before the value of beginLifespanVersion.
Relevant requirements:
IR Requirement Article 10 (3): Life-cycle of Spatial Objects. Where the attributes beginLifespanVersion and endLifespanVersion are used, the value of endLifespanVersion shall not be before the value of beginLifespanVersion.
Verify that identifiers are persistent for a spatial object, i.e. inspect the documentation of the spatial data set and verify that rules for identifiers are specified in a way that the identifiers (namespace and localId) do not change during the life-cycle of a spatial object. If older versions of the data set are available compare the features and verify that the namespace and localId part of the INSPIRE identifiers have not changed between the versions.
Relevant requirements:
IR Requirement Article 9 (2): Identifier Management. The external object identifier for the unique identification of spatial objects shall not be changed during the life-cycle of a spatial object.
Verify that the type of a spatial object is unchanged for different versions, i.e. inspect the documentation of the spatial data set and verify that rules for the mapping to the INSPIRE application schema are specified in a way that the spatial object type do not change during its life-cycle. If older versions of the data set are available compare the features and verify that the types of the features has not changed between the versions.
Relevant requirements:
IR Requirement Article 9 (2): Identifier Management. The external object identifier for the unique identification of spatial objects shall not be changed during the life-cycle of a spatial object.
IR Requirement Article 12 (3): Other Requirements and Rules. Where the attributes validFrom and validTo are used, the value of validTo shall not be before the value of validFrom.
Conformance class: Data consistency, Area Management, Restriction/Regulation Zones
and Reporting Units
1
This test suite examines a data set against theme-specific requirements related to the consistency of the data.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
Verify whether in all cases, where the geometry of a spatial object is derived from another spatial object, the geometries of the two objects are consistent.
For all objects in an AM data set, whose geometry has been derived from another spatial object, compare the geometries of the two objects. The test is passed when the geometries are consistent.
Inspect that the geometry of each instance ManagementRestrictionOrRegulationZone correspond to an edge in the topological structure formed by the complete boundary graph, including the boundaries of all levels.
Conformance class: INSPIRE GML application schemas, General requirements
6
This test suite examines GML documents against basic requirements for the GML encoding for spatial data sets in INSPIRE. This only covers application-schema-independent, generic requirements. Requirements related to specific application schemas are part of conformance classes with a dependency on this conformance class.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
Verify whether each relevant element of the source data set under inspection has been properly mapped to the INSPIRE application schemas. Inspect the documentation of the source data set and determine, if all relevant information has been mapped correctly to the INSPIRE application schema, i.e. that spatial object types, data types, attributes, association roles, code lists, and enumerations are mapped to the INSPIRE application schemas with the correct designation of mnemonic names.
Relevant requirements:
Article 4(1) - For the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC, Member States shall use the spatial object types and associated data types, enumerations and code lists that are defined in Annexes II, III and IV for the themes the data sets relate to.
Inspect the XML Schema namespace of each feature element. If a namespace URI does not start with "http://inspire.ec.europa.eu/schemas/" or "urn:x-inspire:specification:gmlas:" it is not one of the approved INSPIRE application schema namespaces. Review the extension documentation for the identified namespaces to check that any extensions do not overlap with the spatial object types and associated data types and enumerations that are defined in Annexes II, III and IV of the Implementing Rule.
Relevant requirements:
Article 4(1) - For the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC, Member States shall use the spatial object types and associated data types, enumerations and code lists that are defined in Annexes II, III and IV for the themes the data sets relate to.
Validate each document against the schema(s) specified in the xsi:schemaLocation attribute using strict XML schema validation.
Relevant requirements:
IR Requirement Article 3: Common Types. Types that are common to several of the themes listed in Annexes I, II and III to Directive 2007/2/EC shall conform to the definitions and constraints and include the attributes and association roles set out in Annex I.
IR Requirement Article 4 (2): Types for the Exchange and Classification of Spatial Objects. Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in the Annexes.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
IR Requirement Article 5 (2): Types. Types that are a sub-type of another type shall also include all this type‘s attributes and association roles.
IR Requirement Article 5 (3): Types. Abstract types shall not be instantiated.
IR Requirement Article 6 (5): Code Lists and Enumerations. Attributes or association roles of spatial object types or data types that have an enumeration type may only take values from the lists specified for the enumeration type.
IR Requirement Article 9 (1): Identifier Management. The data type Identifier defined in Section 2.1 of Annex I shall be used as a type for the external object identifier of a spatial object.
TG Requirement 1: Spatial object types and data types shall comply with the multiplicities defined for the attributes and association roles in this section.
TG Requirement 6: Data instance (XML) documents shall validate without error against the provided XML schema.
Note that validation is done on a file-by-file basis and access to many remote schema files is time consuming. I.e. it will be much faster to validate a single document with many features than many files with a few features each.
Inspect each property element and verify that it either carries a URI reference to an object (@xlink:href), contains one or more object elements as child elements or contains a non-empty text node (whitespace is trimmed before checking for empty text).
Strictly, empty string values are valid according to the GML model, but they are not an appropriate value for any of the string-valued attributes in INSPIRE.
Relevant requirements:
IR Requirement Article 4 (2): Types for the Exchange and Classification of Spatial Objects. Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in the Annexes.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
Inspect each XML element that represents a feature property and that has a nilReason XML attribute. Verify that xsi:nil='true' is present in the property element, i.e. a reason is only provided in properties that are void / nil.
Limitation: This test currently does not analyse properties of data types or objects embedded in a feature.
Relevant requirements:
IR Requirement Article 4 (2): Types for the Exchange and Classification of Spatial Objects. Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in the Annexes.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
Inspect all nilReason values and verify that either the values from the INSPIRE registry or the pre-defined values from the GML standard are used. Otherwise report incorrectReason. Valid values are:
Limitation: This test currently does not analyse properties of data types or objects embedded in a feature.
Relevant requirements:
IR Requirement Article 4 (2): Types for the Exchange and Classification of Spatial Objects. Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in the Annexes.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
Verify that all features that are not excluded from the default requirement that geometries meet the requirements of the Simple Features standard fulfill the requirements.
Verify that no spatial topology types are used, i.e. check that none of the GML object elements for spatial topology are used as child elements of a feature from the application schema.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Verify that only linear interpolation is used, i.e. check that none of the nonlinear GML curve segment object elements are used as child elements of a feature from the application schema.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Verify that only gml:Polygon or gml:Surface are used, i.e. check that none of the disallowed GML surface object elements are used as child elements of a feature from the application schema.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Verify that only planar interpolation is used, i.e. check that only PolygonPatch is used as a GML surface patch object elements in features from the application schema.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Verify that only valid GML geometry elements are used, i.e. check that none of the disallowed GML geometry object elements are used as child elements of a feature from the application schema.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Verify that in points only gml:pos is used for coordinates.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Verify that in curves and surfaces only gml:posList is used for coordinates.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Verify that geometry aggregates do not use the GML array property elements, i.e. check that the only the regular property elements are used, but not the array property elements. For example, for a gml:MultiPoint, only gml:pointMember may be used, not gml:pointMembers.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Coordinate reference systems may have 1, 2 or 3 dimensions, i.e. check all occurances of srsDimension and for values greater than '3'.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Verify that in curves and surfaces only gml:posList is used for coordinates, i.e. validate all geometry elements of a feature from the application schema using a geometry library.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Note:
Cadastral Parcel and Building 3D features are excluded from this requirement.
Report any errors found while parsing GML geometries.
Relevant requirements:
IR Requirement Article 12 (1): Other Requirements and Rules. The value domain of spatial properties defined in this Regulation shall be restricted to the Simple Feature spatial schema as defined in Herring, John R. (ed.), OpenGIS® Implementation Standard for Geographic information – Simple feature access – Part 1: Common architecture, version 1.2.1, Open Geospatial Consortium, 2011, unless specified otherwise for a specific spatial data theme or type.
Verify whether all attributes whose value type is a code list take the values set out therein. This is usually part of the tests of the corresponding application schema. However, for data types that are used across the INSPIRE application schemas, this is best done in this test suite to avoid duplicating the same test in many test suites. The relevant data types for the Annex I data themes with code list values are: GeographicalName.
When an attribute has a code list as its type, verify that the values comply with the definitions and include the values set out in Annex II of the regulation. For this attribute, the allowed values are specified in code list http://inspire.ec.europa.eu/codelist/GrammaticalNumberValue. For datasets using version 3 of the GML application schema, the value is the last path element of the code list value URI and it is in the child text node. For datasets using version 4 of the GML application schema, the value is in the xlink:href XML attribute and is the HTTP URI of the code list value.
Relevant requirements:
IR Requirement Article 4 (1): Types for the Exchange and Classification of Spatial Objects. For the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC, Member States shall use the spatial object types and associated data types, enumerations and code lists that are defined in Annexes II, III and IV for the themes the data sets relate to.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
IR Requirement Article 6 (1): Code Lists and Enumerations. Codelists shall be of one of the following types, as specified in the Annexes:
code lists whose allowed values comprise only the values specified in this Regulation;
code lists whose allowed values comprise the values specified in this Regulation and
narrower values defined by data providers;
code lists whose allowed values comprise the values specified in this Regulation and
additional values at any level defined by data providers;
code lists, whose allowed values comprise any values defined by data providers.
For the purposes of points 2, 3 and 4, in addition to the allowed values, data providers may use the values specified in the relevant INSPIRE Technical Guidance document available on the INSPIRE web site of the Joint Research Centre.
IR Requirement Article 6 (2): Code Lists and Enumerations. Code lists may be hierarchical. Values of hierarchical code lists may have a more generic parent value. Where the valid values of a hierarchical code list are specified in a table in this Regulation, the parent values are listed in the last column.
IR Requirement Article 6 (3): Code Lists and Enumerations. Where, for an attribute whose type is a code list as referred to in points 2, 3 or 4 of paragraph 1, a data provider provides a value that is not specified in this Regulation, that value and its definition shall be made available in a register.
IR Requirement Article 6 (4): Code Lists and Enumerations. Attributes or association roles of spatial object types or data types whose type is a code list may only take values that are allowed according to the specification of the code list.
When an attribute has a code list as its type, verify that the values comply with the definitions and include the values set out in Annex II of the regulation. For this attribute, the allowed values are specified in code list http://inspire.ec.europa.eu/codelist/GrammaticalGenderValue. For datasets using version 3 of the GML application schema, the value is the last path element of the code list value URI and it is in the child text node. For datasets using version 4 of the GML application schema, the value is in the xlink:href XML attribute and is the HTTP URI of the code list value.
Relevant requirements:
IR Requirement Article 4 (1): Types for the Exchange and Classification of Spatial Objects. For the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC, Member States shall use the spatial object types and associated data types, enumerations and code lists that are defined in Annexes II, III and IV for the themes the data sets relate to.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
IR Requirement Article 6 (1): Code Lists and Enumerations. Codelists shall be of one of the following types, as specified in the Annexes:
code lists whose allowed values comprise only the values specified in this Regulation;
code lists whose allowed values comprise the values specified in this Regulation and
narrower values defined by data providers;
code lists whose allowed values comprise the values specified in this Regulation and
additional values at any level defined by data providers;
code lists, whose allowed values comprise any values defined by data providers.
For the purposes of points 2, 3 and 4, in addition to the allowed values, data providers may use the values specified in the relevant INSPIRE Technical Guidance document available on the INSPIRE web site of the Joint Research Centre.
IR Requirement Article 6 (2): Code Lists and Enumerations. Code lists may be hierarchical. Values of hierarchical code lists may have a more generic parent value. Where the valid values of a hierarchical code list are specified in a table in this Regulation, the parent values are listed in the last column.
IR Requirement Article 6 (3): Code Lists and Enumerations. Where, for an attribute whose type is a code list as referred to in points 2, 3 or 4 of paragraph 1, a data provider provides a value that is not specified in this Regulation, that value and its definition shall be made available in a register.
IR Requirement Article 6 (4): Code Lists and Enumerations. Attributes or association roles of spatial object types or data types whose type is a code list may only take values that are allowed according to the specification of the code list.
When an attribute has a code list as its type, verify that the values comply with the definitions and include the values set out in Annex II of the regulation. For this attribute, the allowed values are specified in code list http://inspire.ec.europa.eu/codelist/NameStatusValue. For datasets using version 3 of the GML application schema, the value is the last path element of the code list value URI and it is in the child text node. For datasets using version 4 of the GML application schema, the value is in the xlink:href XML attribute and is the HTTP URI of the code list value.
Relevant requirements:
IR Requirement Article 4 (1): Types for the Exchange and Classification of Spatial Objects. For the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC, Member States shall use the spatial object types and associated data types, enumerations and code lists that are defined in Annexes II, III and IV for the themes the data sets relate to.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
IR Requirement Article 6 (1): Code Lists and Enumerations. Codelists shall be of one of the following types, as specified in the Annexes:
code lists whose allowed values comprise only the values specified in this Regulation;
code lists whose allowed values comprise the values specified in this Regulation and
narrower values defined by data providers;
code lists whose allowed values comprise the values specified in this Regulation and
additional values at any level defined by data providers;
code lists, whose allowed values comprise any values defined by data providers.
For the purposes of points 2, 3 and 4, in addition to the allowed values, data providers may use the values specified in the relevant INSPIRE Technical Guidance document available on the INSPIRE web site of the Joint Research Centre.
IR Requirement Article 6 (2): Code Lists and Enumerations. Code lists may be hierarchical. Values of hierarchical code lists may have a more generic parent value. Where the valid values of a hierarchical code list are specified in a table in this Regulation, the parent values are listed in the last column.
IR Requirement Article 6 (3): Code Lists and Enumerations. Where, for an attribute whose type is a code list as referred to in points 2, 3 or 4 of paragraph 1, a data provider provides a value that is not specified in this Regulation, that value and its definition shall be made available in a register.
IR Requirement Article 6 (4): Code Lists and Enumerations. Attributes or association roles of spatial object types or data types whose type is a code list may only take values that are allowed according to the specification of the code list.
When an attribute has a code list as its type, verify that the values comply with the definitions and include the values set out in Annex II of the regulation. For this attribute, the allowed values are specified in code list http://inspire.ec.europa.eu/codelist/NativenessValue. For datasets using version 3 of the GML application schema, the value is the last path element of the code list value URI and it is in the child text node. For datasets using version 4 of the GML application schema, the value is in the xlink:href XML attribute and is the HTTP URI of the code list value.
Relevant requirements:
IR Requirement Article 4 (1): Types for the Exchange and Classification of Spatial Objects. For the exchange and classification of spatial objects from data sets meeting the conditions laid down in Article 4 of Directive 2007/2/EC, Member States shall use the spatial object types and associated data types, enumerations and code lists that are defined in Annexes II, III and IV for the themes the data sets relate to.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
IR Requirement Article 6 (1): Code Lists and Enumerations. Codelists shall be of one of the following types, as specified in the Annexes:
code lists whose allowed values comprise only the values specified in this Regulation;
code lists whose allowed values comprise the values specified in this Regulation and
narrower values defined by data providers;
code lists whose allowed values comprise the values specified in this Regulation and
additional values at any level defined by data providers;
code lists, whose allowed values comprise any values defined by data providers.
For the purposes of points 2, 3 and 4, in addition to the allowed values, data providers may use the values specified in the relevant INSPIRE Technical Guidance document available on the INSPIRE web site of the Joint Research Centre.
IR Requirement Article 6 (2): Code Lists and Enumerations. Code lists may be hierarchical. Values of hierarchical code lists may have a more generic parent value. Where the valid values of a hierarchical code list are specified in a table in this Regulation, the parent values are listed in the last column.
IR Requirement Article 6 (3): Code Lists and Enumerations. Where, for an attribute whose type is a code list as referred to in points 2, 3 or 4 of paragraph 1, a data provider provides a value that is not specified in this Regulation, that value and its definition shall be made available in a register.
IR Requirement Article 6 (4): Code Lists and Enumerations. Attributes or association roles of spatial object types or data types whose type is a code list may only take values that are allowed according to the specification of the code list.
Verify that the features provided in the dataset adhere to the constraints specified in the INSPIRE application schema. This is usually part of the tests of the corresponding application schema. However, for data types that are used across the INSPIRE application schemas, this is best done in this test suite to avoid duplicating the same test in many test suites. The relevant data types for the Annex I data themes with constraints are: GeographicalName.
At least one of the two attributes pronunciationSoundLink and pronunciationIPA shall not be void
OCL: "inv: self.pronounciationIPA -> notEmpty() or self.pronounciationSoundLink -> notEmpty()"
Verify that for all features either or both pronunciationSoundLink or pronunciationIPA is not void.
Relevant requirements:
IR Requirement Article 4 (2): Types for the Exchange and Classification of Spatial Objects. Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in the Annexes.
Conformance class: GML application schemas, Area Management, Restriction/Regulation
Zones and Reporting Units
2
This test suite examines the GML encoding of spatial objects specified in the INSPIRE GML application schema 'Area Management, Restriction/Regulation Zones and Reporting Units'.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
IR Requirement Article 3: Common Types. Types that are common to several of the themes listed in Annexes I, II and III to Directive 2007/2/EC shall conform to the definitions and constraints and include the attributes and association roles set out in Annex I.
IR Requirement Article 4 (2): Types for the Exchange and Classification of Spatial Objects. Spatial object types and data types shall comply with the definitions and constraints and include the attributes and association roles set out in the Annexes.
IR Requirement Article 4 (3): Types for the Exchange and Classification of Spatial Objects. The enumerations and code lists used in attributes or association roles of spatial object types or data types shall comply with the definitions and include the values set out in Annex II. The enumeration and code list values are uniquely identified by language-neutral mnemonic codes for computers. The values may also include a language-specific name to be used for human interaction.
IR Requirement Article 5 (2): Types. Types that are a sub-type of another type shall also include all this type‘s attributes and association roles.
IR Requirement Article 5 (3): Types. Abstract types shall not be instantiated.
IR Requirement Article 6 (5): Code Lists and Enumerations. Attributes or association roles of spatial object types or data types that have an enumeration type may only take values from the lists specified for the enumeration type.
IR Requirement Article 9 (1): Identifier Management. The data type Identifier defined in Section 2.1 of Annex I shall be used as a type for the external object identifier of a spatial object.
TG Requirement 1: Spatial object types and data types shall comply with the multiplicities defined for the attributes and association roles in this section.
TG Requirement 6: Data instance (XML) documents shall validate without error against the provided XML schema.
Conformance class: Application Schema, Area Management, Restriction/Regulation Zones
and Reporting Units
2
This test suite examines requirements associated with the application schema.
This is a draft version. It has limitations and is expected to contain errors. Please report any issues or problems in GitHub.
Known limitations are documented in the description of the applicable test case or test assertion. There is a general limitation in all assertions that extensions in additional application schemas are only supported, if the unqualified name of the feature type in the extension is the same as the name of the feature type in the INSPIRE application schema.
When an attribute has a code list as its type, verify that the values comply with the definitions and include the values set out in Annex II, III and IV of the Implementing Rule. To pass this test verify that any instance of an attribute:
takes only values explicitly specified in the INSPIRE code list register when the code list‘s extensibility is 'none'.
takes only a value explicitly specified in the INSPIRE code list register or shall take a value that is narrower (i.e. more specific) than those explicitly specified in the application schema when the code list‘s extensibility is 'narrower'.
The following check is performed for every feature in the dataset, for the not extensible codelist:
Check that all the environmentalDomain elements has a xlink:href attribute pointing to a valid value. If the check fails report disallowedCodeListValue.
When an attribute has a code list as its type, verify that the values comply with the definitions and include the values set out in Annex II, III and IV of the Implementing Rule. To pass this test verify that any instance of an attribute:
takes only values explicitly specified in the INSPIRE code list register when the code list‘s extensibility is 'none'.
takes only a value explicitly specified in the INSPIRE code list register or shall take a value that is narrower (i.e. more specific) than those explicitly specified in the application schema when the code list‘s extensibility is 'narrower'.
The following check is performed for every feature in the dataset, for the open codelist:
Check that all the zoneType elements has a xlink:href attribute pointing to a pre-defined value. If the check fails a manual check will be required asking to review the code list definition in order to verify that any extensions do not overlap with the code lists that are defined in Annexes II, III and IV of the Implementing Rule. If the check fails report reviewCodeListValue.
The following checks are performed for every feature in the dataset.
Check if legalBasis is provided and it is not null. If it is provided, with xlink:href attribute or LegislationCitation child element, then: Require to check manually that "At least the most specific legal instrument that required the establishment of zone is provided using the legalBasis association role.".